Introduce new managed Control Plane Operator component - #14
Merged
openshift-merge-robot merged 1 commit intoFeb 5, 2021
Merged
Conversation
openshift-ci-robot
added
the
do-not-merge/work-in-progress
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ironcladlou The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
openshift-ci-robot
added
the
approved
Split out a new Control Plane Operator which is managed by the HyperShift Operator. The Control Plane Operator is a component deployed into each hosted cluster's namespace that manages the rollout and upgrade of a single version of the the cluster's control plane. Its key responsibilities are: - Provisioning all the infrastructure required to host a control plane (whether this means creating or adopting existing infrastructure). This infrastructure may be management cluster resources, external cloud provider resources, etc. - Deploying an OCP control plane (into the operator's namespace), configured to run in the context of the provisioned infrastructure. - Owning and implementing any behavior necessary to rollout (upgrade) the new version (e.g. version specific changes at layers above OCP itself, e.g. configuration or infrastructure changes). The Control Plane Operator is versioned in line with OCP versions it knows how to deploy and manage and is not coupled to the management cluster's version.
ironcladlou
force-pushed
the
control-plane-operator
branch
from
February 5, 2021 16:10
ac4aafa to
2a79d49
Compare
ironcladlou
changed the title
openshift-ci-robot
removed
the
do-not-merge/work-in-progress
Contributor
|
Things work well for me, ship it! :) |
zanetworker
pushed a commit
to zanetworker/hypershift
that referenced
this pull request
Sep 28, 2021
nodePool and capi machines
zanetworker
pushed a commit
to zanetworker/hypershift
that referenced
this pull request
Sep 28, 2021
zanetworker
pushed a commit
to zanetworker/hypershift
that referenced
this pull request
Sep 28, 2021
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Split out a new Control Plane Operator which is managed by the HyperShift
Operator.
The Control Plane Operator is a component deployed into each hosted cluster's
namespace that manages the rollout and upgrade of a single version of the the
cluster's control plane. Its key responsibilities are:
Provisioning all the infrastructure required to host a control plane (whether
this means creating or adopting existing infrastructure). This infrastructure
may be management cluster resources, external cloud provider resources, etc.
Deploying an OCP control plane (into the operator's namespace), configured to
run in the context of the provisioned infrastructure.
Owning and implementing any behavior necessary to rollout (upgrade) the new
version (e.g. version specific changes at layers above OCP itself, e.g.
configuration or infrastructure changes).
The Control Plane Operator is versioned in line with OCP versions it knows how
to deploy and manage and is not coupled to the management cluster's version.